Some Macs recently received a macOS system update which disabled the simulator runtimes used by Xcode 15, including the simulators for iOS, tvOS, watchOS, and visionOS. If your Mac received this update, you will receive the following error message and will be unable to use the simulator:
The com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime is not available.
Domain: com.apple.CoreSimulator.SimError
Code: 401
Failure Reason: runtime profile not found using "System" match policy
Recovery Suggestion: Download the com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime from the Xcode
To resume using the simulator, please reboot your Mac. After rebooting, check Xcode Preferences → Platforms to ensure that the simulator runtime you would like to use is still installed. If it is missing, use the Get button to download it again.
The Xcode 15.3 Release Notes are also updated with this information.
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Posts under Xcode tag
200 Posts
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I have an Xcode app where currently txt files in the project display text data as a list. I can search through the lists and have buttons that will swap between different lists of information that you can look through.
The next task is I have URL connections to docx files on a SharePoint site. I am trying to use an URLsession function to connect to the URL links to download the documents to the document directory then have the application read the doc information to then be displayed as the txt info would.
The idea is that the docx files are a type of online update version of the data. So when the app is used and on wifi, the app can update the list data with the docx files.
I have code set up that should access the URL files but I am struggling to figure out how to read the data and access from this Documents directory. I have been looking online and so far I am at a loss on where to go here.
If anyone can help or provide some insight I would greatly appreciate it.
I can try and provide code samples to help explain things if that is needed.
Archive failing while executing command:
xcodebuild -project Unity-VisionOS.xcodeproj -scheme Unity-VisionOS -destination generic/platform=xros archive -archivePath Unity-VisionOS.xcarchive -quiet > logs/visionos_archive.log
Next error happens:
2025-11-18 15:33:12.161 ibtoold[56062:4395005] [MT] IBPlatformTool: *** Failed to launch tool with description <IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null): Failed to find or create execution context for description '<IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null)'.
Device type: IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x)
Sim runtime: visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
Device: (null)
** Please also include the output of `xcrun simctl diagnose` and `xcode-select -p`.: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Failure reason: Failed to create new simulator device in set SimDeviceSet : /Users/user/Library/Developer/Xcode/UserData/IB Support/Simulator Devices that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Incompatible device). Available devices: (
"IBSimDeviceTypeiPad3x (D1B76A51-0DB5-439F-B65D-891AB20C2B26, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (CA17569D-D3EA-4B11-A20D-3571D4A5E58A, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (E3EE1BC6-2F2F-48D3-A378-A819824F7082, iOS 18.1, Shutdown)"
)): Incompatible device
/* com.apple.ibtool.document.warnings */
/Users/xcode_dir_path/xcode/LaunchScreen-iPhone.storyboard:global: warning: Compiling Interface Builder products for visionOS will not be supported in a future version of Xcode. [9]
/* com.apple.ibtool.errors */
/Users/xcode_dir_path/LaunchScreen-iPhone.storyboard: error: Failed to find or create execution context for description '<IBVisionPlatformToolDescription: 0x600003278380> System content for IBCocoaTouchFramework-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600003278400> scaleFactor=2x, renderMode.identifier=(null)'.
Device type: IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x)
Sim runtime: visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
Device: (null)
** Please also include the output of `xcrun simctl diagnose` and `xcode-select -p`.
Underlying Errors:
Description: Failed to find a suitable device for the type IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) with runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
Failure Reason: Failed to create new simulator device in set SimDeviceSet : /Users/user/Library/Developer/Xcode/UserData/IB Support/Simulator Devices that matches IBSimDeviceTypeiPad2x (com.apple.dt.Xcode.IBSimDeviceType.iPad-2x) for runtime visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1 (Incompatible device). Available devices: (
"IBSimDeviceTypeiPad3x (D1B76A51-0DB5-439F-B65D-891AB20C2B26, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (CA17569D-D3EA-4B11-A20D-3571D4A5E58A, iOS 18.1, Shutdown)",
"IBSimDeviceTypeiPad2x (E3EE1BC6-2F2F-48D3-A378-A819824F7082, iOS 18.1, Shutdown)"
)
Underlying Errors:
Description: Incompatible device
It appears when command was executed from TeamCity. And when it launches manually from console, it works fine.
I tried reinstalling SDK, switching different Xcode versions, removing cache, clearing IB folder, nothing helps.
xcrun simctl list
command prints next:
== Device Types ==
iPhone 17 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-17-Pro)
iPhone 17 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-17-Pro-Max)
iPhone Air (com.apple.CoreSimulator.SimDeviceType.iPhone-Air)
iPhone 17 (com.apple.CoreSimulator.SimDeviceType.iPhone-17)
iPhone 16 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Pro)
iPhone 16 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Pro-Max)
iPhone 16e (com.apple.CoreSimulator.SimDeviceType.iPhone-16e)
iPhone 16 (com.apple.CoreSimulator.SimDeviceType.iPhone-16)
iPhone 16 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-16-Plus)
iPhone 15 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro)
iPhone 15 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Pro-Max)
iPhone 15 (com.apple.CoreSimulator.SimDeviceType.iPhone-15)
iPhone 15 Plus (com.apple.CoreSimulator.SimDeviceType.iPhone-15-Plus)
iPhone 14 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-14-Pro)
...
Apple Vision Pro (com.apple.CoreSimulator.SimDeviceType.Apple-Vision-Pro-4K)
Apple Vision Pro (com.apple.CoreSimulator.SimDeviceType.Apple-Vision-Pro)
iPod touch (7th generation) (com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-)
== Runtimes ==
iOS 18.1 (18.1 - 22B81) - com.apple.CoreSimulator.SimRuntime.iOS-18-1
iOS 18.6 (18.6 - 22G86) - com.apple.CoreSimulator.SimRuntime.iOS-18-6
visionOS 2.1 (2.1 - 22N580) - com.apple.CoreSimulator.SimRuntime.xrOS-2-1
== Devices ==
-- iOS 18.1 --
iPhone 16 Pro (78683AE0-6238-4EF1-BD47-192FC0DC2559) (Shutdown)
iPhone 16 Pro Max (98BFE915-787D-4673-991A-5D3EC448CC51) (Shutdown)
iPhone 16 (D3E6FED8-9E65-4141-A31C-FC7EA3492111) (Shutdown)
...
iPad mini (A17 Pro) (10F1862E-E27B-42C5-9B02-1FA71D2F4707) (Shutdown)
iPad (10th generation) (E6E0D31F-91E4-4D3E-898D-516D79DDD58E) (Shutdown)
-- visionOS 2.1 --
Apple Vision Pro (E4D22A75-A38E-4135-9152-EF4D64BEC3F2) (Shutdown)
Subject: Xcode Cloud not detecting ci_scripts/ci_post_clone.sh for Flutter iOS build Description: I'm attempting to build a Flutter iOS app using Xcode Cloud, but the build is failing because Xcode Cloud cannot detect my custom build script located at ci_scripts/ci_post_clone.sh in the repository root. Setup:
Repository: https://github.com/GlamTam2000/King-chi-app
Branch: ios-build-legacy
Xcode Project: flutter_application_1/ios/Runner.xcworkspace
Xcode Version specified: 15.4
Issue: The Xcode Cloud build logs consistently show:
Post-Clone script not found at ci_scripts/ci_post_clone.sh
However, the script file is confirmed to exist in the repository:
The file is committed and pushed to GitHub (commit 9bd3aa1)
Local git verification: git ls-tree HEAD ci_scripts/ shows the file exists
File permissions: 100755 (executable)
File location: Repository root /ci_scripts/ci_post_clone.sh
What I've tried:
Created ci_scripts/ci_post_clone.sh at repository root with executable permissions
Ensured Unix line endings (LF, not CRLF)
Removed macOS extended attributes
Tried both ci_post_clone.sh and ci_pre_xcodebuild.sh scripts
Created empty commits to force Xcode Cloud to fetch latest changes
Verified the file exists locally and in git history
Why I need this script: Flutter requires running flutter build ios --release --no-codesign before Xcode can build, which generates the FlutterGeneratedPluginSwiftPackage that Xcode depends on. Without this script running, the build fails with:
Could not resolve package dependencies: the package at '.../FlutterGeneratedPluginSwiftPackage' cannot be accessed
Question: Why is Xcode Cloud not detecting the ci_scripts/ci_post_clone.sh file even though it exists in the repository root? Is there a specific configuration in App Store Connect or a Xcode Cloud workflow setting that needs to be enabled for custom scripts to run? Additional files in repository (also not working):
.xcode-version at repository root (specifying 15.4)
.xcodecloud.yml at repository root (with workflow configuration)
Any guidance on how to make Xcode Cloud properly detect and execute custom build scripts would be greatly appreciated.
This gives Apple Support all the key information they need to help diagnose why the scripts aren't being detected.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Xcode Server
Swift
Xcode
Hey!
I am writing type formatting scripts in Python for lldb, as described in https://lldb.llvm.org/use/variable.html#python-scripting. I'm trying to pass an environment variable to lldb from Xcode to determine the path to the scripts in the project root, so the project is not bound to some predetermined path. I am having trouble doing this in Xcode.
What I have tried:
lldbinit file
Create a .lldbinit file in $(SRCROOT) with the following content: platform shell echo $SRCROOT.
Set the path to the .lldbinit file in Edit Scheme... > Info > LLDB Init File ($(SRCROOT)/.lldbinit).
Set the SRCROOT environment variable to $(SRCROOT) in Edit Scheme... > Arguments > Environment Variables.
entry-point breakpoint
Add a breakpoint to the entry-point of the application.
Set the Automatically continue after evaluating actions option.
Add the action platform shell $(SRCROOT) or platform shell $SRCROOT.
Set the SRCROOT environment variable to $(SRCROOT) in Edit Scheme... > Arguments > Environment Variables.
What I expect to happen: The first line of the debug console is a path pointing to $(SRCROOT)
What actually happens: No path is output
Is this functionality available in Xcode Version 26.0.1 (17A400)?
Thanks in advance,
Barnabas
The application crashes immediately when the system attempts to display the automatic password input view controller (_SFAutomaticPasswordInputViewController). This occurs during the login or password-filling process.
OS Version: iOS 26.2 Beta 1
Build Number: (23C5027f)
Fatal Exception: NSInvalidArgumentException
*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil
Description
On iOS 26.1, a ToolbarItem placed in .keyboard is no longer exposed to the accessibility hierarchy. As a result:
VoiceOver cannot focus or activate the toolbar button
XCUITest cannot discover the element, making the UI impossible to test
TextEditor()
.toolbar {
ToolbarItem(placement: .keyboard) {
Button("Done") { /* action */ }
}
}
This worked correctly on previous iOS versions.
The button appears visually but is missing from both VoiceOver navigation and XCUI accessibility queries.
Steps to Reproduce
Create a new SwiftUI project.
Use a simple text field with a keyboard toolbar button.
Run on an iOS 26.1 device or simulator.
Focus the text field to show the keyboard.
Turn on VoiceOver and attempt to navigate to the toolbar button.
Run an XCUITest attempting to locate the button
CRITICAL: iOS 26.1 Simulator Runtime (Build 23B86) Missing / MobileAsset Catalog Failing
Summary
After updating macOS and Xcode, I can no longer download or install the required iOS 26.1 simulator runtime. The Xcode Components system fails for all assets, and the MobileAsset catalog for iOS simulator runtimes appears to be missing or invalid. The runtime is also not listed on developer.apple.com.
This issue blocks me from running any iOS simulators.
Steps to Reproduce
Update to:
macOS 26.1 (25B78)
Xcode 26.1.1 (24455 / 17B100)
Open Xcode → Settings → Platforms/Components
Attempt to download:
iOS 26.1 Simulator Runtime
Any other downloadable component (e.g., Predictive Code Completion Model)
Alternatively, try using:
xcodebuild -downloadPlatform iOS -exportPath ~/Downloads
xcodebuild -downloadPlatform iOS -buildVersion 26
Observed Behaviour
Xcode Components Downloads Fail
Attempting to download the iOS 26.1 runtime results in:
Download failed.
Domain: DVTDownloadableErrorDomain
Code: 41
Additional detail:
Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime)
Domain: DVTDownloadsUtilitiesErrorDomain
Code: -1
And:
Download failed due to a bad URL.
Domain: com.apple.MobileAssetError.Download
Code: 49
User Info: { checkConfiguration = 1 }
Predictive Code Completion Model Also Fails
The operation couldn’t be completed. (IDELanguageModelKit.IDEModelDownloadAdapter.DownloadError error 2.)
Domain: IDELanguageModelKit.IDEModelDownloadAdapter.DownloadError
Code: 2
There was an error transferring over the network.
Code: 2
CLI Downloads Fail
Command:
xcodebuild -downloadPlatform iOS -exportPath ~/Downloads
Result:
DVTDownloadable: Download Failed … iOS 26.1 Simulator (23B86)
Command:
xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26
Result:
iOS 26 is not available for download.
Runtime Not Listed on Developer Downloads
The following page does not list iOS 26.1 simulator runtime:
https://developer.apple.com/download/all/
Expected Behaviour
Xcode should be able to fetch the MobileAsset catalog and download iOS 26.1 simulator runtime.
The runtime should appear in the Components tab and on developer.apple.com/download/all/.
CLI tools should successfully download the platform.
System Information
macOS: 26.1 (Build 25B78)
Xcode: 26.1.1 (24455) (Build 17B100)
Timestamp: 2025-11-17
Impact
This issue currently prevents:
Running any iOS simulator
Testing or building on the required runtime
Using other Xcode downloadable components (language models, etc.)
This is a blocking issue for development.
Notes
Multiple Xcode reinstallations attempted
macOS restarts performed
Network connectivity normal
Issue persists across all download methods (GUI + CLI)
Hello,
I am facing a recurring issue with Xcode iOS simulator (preview). I want to preview a SwiftUI for iOS in Xcode, but the Simulator app fails to boot up.
I receive the following error in Xcode:
Cannot Preview in this file. Simulator was shutdown during an update.
I have tried the following:
Completely uninstalling XCode and deleting all developer data, then reinstalling everthing again.
Shutdown and restart
Deleting all developer data, deleting XCode cache
Reinstalling iOS Simulator runtimes and reconfiguration of simulators.
Tested using different simulator and runtime versions.
"xcrun simctl --set previews delete al"
My reported issues:
FB20987522
FB20485454
Thank you
Best regards,
Jens
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode Previews
Xcode
Simulator
Business and Enterprise
I'm unable to sign the an example application using xcode and "automatically manage signing".
The error I'm getting is:
CodeSign [...] (in target 'foobar' from project 'foobar')
Signing Identity: "Apple Development: [xxxx] "
/usr/bin/codesign --force --sign 4ABB258102FF656E9F597546A49274C28D2B8B3E -o runtime --timestamp\=none --generate-entitlement-der [filename]
4ABB258102FF656E9F597546A49274C28D2B8B3E: no identity found
Command CodeSign failed with a nonzero exit code
However, I am able to see a certificate and a private identity on my keychain:
% security find-certificate -aZ | grep -i 4ABB258102FF656E9F597546A49274C28D2B8B3E
SHA-1 hash: 4ABB258102FF656E9F597546A49274C28D2B8B3E
and
% security find-key -s | grep -q 'Apple Development' && echo YES
YES
what is puzzling is that security does not find an identity:
% security find-identity -p codesigning
Policy: Code Signing
Matching identities
0 identities found
Valid identities only
0 valid identities found
but XCode claims that everything is working fine.
Anybody knows what might I be missing?
I tried logging out, requesting new certificates, rebooting, moving them to another keychain, and asking to developer friends.
I'm reading a bit outdated book about Cocoa/Objective-C applications development and I'm trying to code some examples. And so I ended up with an almost empty NSDocument-based app with runtime errors like that:
Internal inconsistency in menus - menu <NSMenu: 0xbc726d040>
Title: Window
Supermenu: 0xbc726d080 (Main Menu), autoenable: YES
Previous menu: 0x0 (None)
Next menu: 0x0 (None)
Items: (
"<NSMenuItem: 0xbc6fcd9a0 Minimize, ke='Command-M'>",
"<NSMenuItem: 0xbc6fcda40 Zoom, ke mask=''>",
"<NSMenuItem: 0xbc6fcdae0, separator, ke mask=''>",
"<NSMenuItem: 0xbc6fcd900 Bring All to Front, ke mask=''>"
) believes it has <NSMenu: 0xbc726d080>
Title: Main Menu
Supermenu: 0x0 (None), autoenable: YES
Previous menu: 0x0 (None)
Next menu: 0x0 (None)
Items: (
) as a supermenu, but the supermenu does not seem to have any item with that submenu
It looks like as if the menu tries to include itself as a submenu. Am I right? I have no ideas what led to this. If I'm not mistaken this has started since macOS Tahoe.
The code that is not a boilerplate one I have:
// Document.m
#import "Document.h"
@implementation Document
@synthesize text;
- (NSString *)windowNibName {
return @"SampleDocument";
}
- (void)windowControllerDidLoadNib:(NSWindowController *)aController {
[super windowControllerDidLoadNib:aController];
if (self.text == nil) {
self.text = @"";
}
self.textField.stringValue = self.text;
}
- (NSData *)dataOfType:(NSString *)typeName error:(NSError **)outError {
self.text = self.textField.stringValue;
return [self.text dataUsingEncoding:NSUTF8StringEncoding];
}
- (BOOL)readFromData:(NSData *)data ofType:(NSString *)typeName error:(NSError **)outError {
if ([data length] > 0) {
NSString * string = [[NSString alloc] initWithData:data encoding:NSUTF8StringEncoding];
self.text = string;
}
else {
self.text = @"";
}
return YES;
}
+ (BOOL)autosavesInPlace {
return YES;
}
@end
There are two xib's: MainMenu.xib and Document.xib but I won't include them here.
Please advise how to fix this menu issue.
I just submitted a feedback for this (FB9662125) but in the spirit of “share and enjoy”…
The cool new Generate Info.plist File feature in Xcode 13 crashes if you try to put an NSLocationTemporaryUsageDescriptionDictionary in your Info.plist file. Here’s a simple repro scenario:
Create a minimal iOS app (no Core Data, no tests)
Go to target settings → Info tab → Custom iOS Target Properties
Click the (+) button on any row to begin inserting a new row
Select Privacy - Location Temporary Usage Description Dictionary
Click somewhere else or press Return to commit the selection
Xcode crashes immediately
More generally, it seems that Xcode crashes any time it tries to regenerate your Info.plist file if it contains an NSLocationTemporaryUsageDescriptionDictionary, even if (for example) you manually pasted that dictionary into the file earlier. In that case, merely tapping the (+) button in step 3 above is enough to crash it.
Hey there!
I recently noticed that when using Xcode Code Intelligence, it repeats itself within the response. Is this a normal occurrence, or is there an issue with the LLM itself? I’m using MistralAI Codestral as my LLM.
Hello - I’m the Account Holder for an individual Apple Developer Program account. I’m working with freelance junior developers who are building my app in React Native mainly in TypeScript (.tsx) with some JavaScript, with code in GitHub. The app currently runs in Expo Go now.
I’ve been directed to this forum for step-by-step guidance. Specifically I need clear, sequential instructions I can give my developers (and what I personally must do on my Mac) so they can produce a properly signed iOS build for TestFlight (internal testing), and Upload that build to App Store Connect and then submit the release to the App Store.
Context:
This is an individual developer account (not an organization).
I am the only person with a Mac. I added them as developers but was told I need to be the one to upload the final build (is this true, and if so, what do they send me to do that, and when they send it to me, can you please tell me exactly what I need to do from there?)
I was told about Swift Playground, possible SwiftUI conversion if needed, APK file, and using my Xcode for final submission, but not sure what to make of this that will get it on TestFlight from the current React Native.
What I would like to ask for help with is a concise, step-by-step checklist (including exact menu names / commands or tools like EAS Submit, Transporter, or Xcode) of the developers' steps and my admin/account holder steps, so I can hand it to the developers and make sure nothing is missed to get on TestFlight.
I’m on a tight timeline, so any clear, detailed guidance would be extremely appreciated.
Thank you so much. I have looked everywhere and cannot find a step-by-step!
Several app developers are struggling with the inability to provide a separate app icons that looks nice on older macOS versions while at the same time provide Icon Composer icons that look great on macOS Tahoe 26. An ability to provide separate icons is super important to those who have app icons that follow the curvature of the default icon borders (as the corner rounding radius is different for Sequia and Tahoe). Take a look at this for example:
https://github.com/ghostty-org/ghostty/issues/7564#issuecomment-3042061547
Question: Is there a definitive/recommended way to address this issue? How can a developer add a glass icon variant that looks good on Tahoe and provide a bitmap icon for older macOS versions?
Some background info:
Prior to Xcode 26 beta 4, one could add an App Icon to Assets to be used as app icon for legacy macOS versions (Sequia and older) and use a new Icon Composer icon (placed in the project root) for macOS Tahoe 26. Enabling "Include all app icon assets" under target settings ensured that older macOS versions would use the old app icons while Tahoe the new Icon Composer glass one.
Since Xcode beta 4 this technique no longer works. Xcode instead insists on populating Assets.car with Icon Composer generated variants, disregarding the App Icon provided in Assets. Although the App Icon in Assets makes its way to a .incs file in the app bundle's Contents/Resources folder, but that is not used by macOS anymore and is there for some compatibility purposes. The Assets.car file (which matters) only contains the variants generated by Icon Composer and does not contain the png icons provided in the Assets.
Hi everyone,
I’m currently unable to view crash logs in Xcode Organizer for any of the apps in my account. When I try to access crash reports, I receive the following error:
"An error occurred preventing Xcode from downloading version information from App Store Connect. An unexpected error occurred: [<__NSDictionaryM> valueForUndefinedKey:]: this class is not key value coding-compliant for the key [App Name] [Version] (iOS App)."
The error message references an app name and version that were previously used. Notably, the original app name included an @ symbol (e.g., @ExampleApp). We suspected this might be contributing to the issue, so we updated the app name to remove the symbol. However, the error persists and still references the old name.
Has anyone experienced something similar or found a workaround? Any guidance would be greatly appreciated!
Thanks in advance.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Xcode
Analytics & Reporting
As subject, after update to Xcode 26.0.1, none of the simulator able to download, tried click the Get button, tried run command in terminal, all failed.
Error from terminal:
xcodebuild -downloadPlatform iOS
Finding content...
Automatically resolved architecture variant for platform iOS as 'universal'.
2025-10-09 06:21:24.423 xcodebuild[1789:30064] DVTDownloadable: Download Failed. Downloadable: {
architectures = (
arm64,
"x86_64"
);
authentication = none;
category = simulator;
contentType = cryptexDiskImage;
dictionaryVersion = 2;
downloadMethod = mobileAsset;
fileSize = 10066611438;
identifier = "com.apple.dmg.iPhoneSimulatorSDK26_0";
isInternalContent = 0;
isUserInitiated = 1;
name = "iOS 26.0 Universal Simulator (23A343)";
patchableFrom = (
);
platform = "com.apple.platform.iphoneos";
simulatorVersion = {
buildUpdate = 23A343;
version = "26.0";
};
version = "26.0.0.0";
}. Download failed.
Any idea how to resolve this?
iMac with Intel processor
I am using MacOS 26.1 and Xcode 26.1; my existing project cannot select a simulator, but creating a new project allows me to select a simulator normally.
I am using Automatically Manage Signing
And I have registered my Mac UUID in developer account, but it is still giving me these errors -
Device My Mac is not registered to your team Ai Glider Inc. Devices must be registered in order to run your code, but you do not have permission to register them. Please check with your team's admin.
No profiles for 'com.aiexample.sebexample' were found
Xcode couldn't find any Mac App Development provisioning profiles matching 'com.aiexample.sebexample'.
I have placed a .contextignore file next to my .xcworkspace file, it's contents look like this:
CHANGELOG.md
*.generated.swift
*.mockingbird.swift
However I'm still getting files that match these globs in my project context requests when using Coding Intelligence with a 3rd party provider (Gemini)
What am I doing wrong?
We got an app for iPad which has two targets one for the App itself (MainApp target ) and another one for the Driver ( Driver Target ) using DriverKit.
The app works fine in Development, but I'm trying to distribute it with adhoc.
I've requested the Distribution Entitlement to Apple, after getting it, the App Id for the Driver has the following Capabilities:
DriverKit, DriverKit (development), DriverKit USB Transport (development), DriverKit USB Transport - VendorID, In-App Purchase
Now in the profile section, I've created a adhoc profile for the Driver AppId (Identifier). Obviously I've also created an Adhoc profile for the Main AppId
Finally in the Signing & Capabilities Section I set up the profiles for MainApp target, int the Debug one I set up the Development one and int the Release one I set up the adhoc one.
I do the same in the Driver Target, but when I set up the Adhoc one in the Release, I've got a warning:
Xcode 14 and later requires a DriverKit development profile enabled for iOS and macOS. Visit the developer website to create or download a DriverKit profile
Also interestingly the Signing Certificate section says: None
I also set up the Capabilities for the Driver Target:
DriverKit USB Transport - VendorID
DriverKit USB Transport ( Development )
Inside these capabilities I set up the vendor ID as dictionary
The problem is, if I try to Archive the app I will get the previous Warning message as error:
Xcode 14 and later requires a DriverKit development profile enabled for iOS and macOS. Visit the developer website to create or download a DriverKit profile.
Any idea what I'm missing?
Thanks
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
iPadOS
Xcode
Provisioning Profiles
DriverKit